`:top
`! Java Management Extensions`! (`!JMX`!) is a `F33f`_`[Java`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_platform]`_`f technology that supplies tools for managing and monitoring `F33f`_`[applications`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Application_software]`_`f, system objects, devices (such as `F33f`_`[printers`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Computer_printer]`_`f) and service-oriented networks. Those resources are represented by objects called MBeans (for `*`F33f`_`[Managed Bean`#managed-beans]`_`f`*). In the API, `F33f`_`[classes`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Class_(computer_science)]`_`f can be dynamically loaded and instantiated. Managing and monitoring applications can be designed and developed using the Java Dynamic Management Kit.`:cite-ref-1[`F5bf`_`[1`#cite-note-1]`_`f]
JSR 003`:cite-ref-2[`F5bf`_`[2`#cite-note-2]`_`f] of the `F33f`_`[Java Community Process`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_Community_Process]`_`f defined JMX 1.0, 1.1 and 1.2. JMX 2.0 was being developed under JSR 255, but this JSR was subsequently withdrawn.`:cite-ref-3[`F5bf`_`[3`#cite-note-3]`_`f] The JMX Remote API 1.0 for remote management and monitoring is specified by JSR 160.`:cite-ref-4[`F5bf`_`[4`#cite-note-4]`_`f] An extension of the JMX Remote API for Web Services was being developed under JSR 262.`:cite-ref-5[`F5bf`_`[5`#cite-note-5]`_`f]
Adopted early on by the `F33f`_`[J2EE`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_Platform,_Enterprise_Edition]`_`f community, JMX has been a part of `F33f`_`[J2SE`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_Platform,_Standard_Edition]`_`f since version 5.0. "JMX" is a trademark of `F33f`_`[Oracle Corporation`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Oracle_Corporation]`_`f.
>>Contents
• `F0af`_`[Architecture`#architecture]`_`f
• `F0af`_`[Managed beans`#managed-beans]`_`f
• `F0af`_`[Types`#types]`_`f
• `F0af`_`[Support`#support]`_`f
• `F0af`_`[See also`#see-also]`_`f
• `F0af`_`[References`#references]`_`f
• `F0af`_`[Further reading`#further-reading]`_`f
• `F0af`_`[Articles`#articles]`_`f
• `F0af`_`[Books`#books]`_`f
• `F0af`_`[External links`#external-links]`_`f
-─
>>Architecture
JMX uses a three-level architecture:
1. The `*Probe`* level – also called the `*Instrumentation`* level – contains the probes (called `F33f`_`[MBeans`#managed-beans]`_`f) `F33f`_`[instrumenting`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Instrumentation_(computer_programming)]`_`f the resources
2. The `*Agent`* level, or MBeanServer – the core of JMX. It acts as an intermediary between the MBean and the applications.
3. The `*Remote Management`* level enables remote applications to access the MBeanServer through connectors and adaptors. A connector provides full remote access to the MBeanServer API using various communication (`F33f`_`[RMI`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_remote_method_invocation]`_`f, `F33f`_`[IIOP`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=IIOP]`_`f, `F33f`_`[JMS`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_Message_Service]`_`f, `F33f`_`[WS-*`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=List_of_web_service_specifications]`_`f …), while an adaptor adapts the API to another protocol (`F33f`_`[SNMP`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Simple_Network_Management_Protocol]`_`f, …) or to Web-based GUI (`F33f`_`[HTML`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=HTML]`_`f/`F33f`_`[HTTP`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=HTTP]`_`f, `F33f`_`[WML`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Wireless_Markup_Language]`_`f/`F33f`_`[HTTP`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=HTTP]`_`f, …).
Applications can be generic consoles (such as `F33f`_`[JConsole`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=JConsole]`_`f`:cite-ref-6[`F5bf`_`[6`#cite-note-6]`_`f] and `F33f`_`[MC4J`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=MC4J]`_`f`:cite-ref-7[`F5bf`_`[7`#cite-note-7]`_`f]) or domain-specific (monitoring) applications. External applications can interact with the MBeans through the use of JMX connectors and protocol adapters. Connectors serve to connect an agent with a remote JMX-enabled management application. This form of communication involves a connector in the JMX agent and a connector client in the management application.
The `F33f`_`[Java Platform, Standard Edition`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_Platform,_Standard_Edition]`_`f ships with one connector, the `!RMI connector`!, which uses the Java Remote Method Protocol that is part of the `F33f`_`[Java remote method invocation`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_remote_method_invocation]`_`f API. This is the connector which most management applications use.
Protocol adapters provide a management view of the JMX agent through a given protocol. Management applications that connect to a protocol adapter are usually specific to the given protocol.
>>Managed beans
A `!managed bean`! – sometimes simply referred to as an `*MBean`* – is a type of `F33f`_`[JavaBean`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=JavaBean]`_`f, created with `F33f`_`[dependency injection`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Dependency_injection]`_`f. Managed Beans are particularly used in the Java Management Extensions technology – but with Java EE 6 the specification provides for a more detailed meaning of a managed bean.
The MBean represents a resource running in the `F33f`_`[Java virtual machine`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_virtual_machine]`_`f, such as an application or a Java EE technical service (transactional monitor, JDBC driver, etc.). They can be used for collecting statistics on concerns like performance, resources usage, or problems (pull); for getting and setting application configurations or properties (push/pull); and notifying events like faults or state changes (push).
Java EE 6 provides that a managed bean is a bean that is implemented by a Java class, which is called its bean class. A top-level Java class is a managed bean if it is defined to be a managed bean by any other Java EE technology specification (for example, the `F33f`_`[JavaServer Faces`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=JavaServer_Faces]`_`f technology specification), or if it meets all of the following conditions:
1. It is not a non-static `F33f`_`[inner class`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Inner_class]`_`f.
2. It is a concrete class, or is annotated `B100`F9d9@Decorator`f`b.
3. It is not annotated with an EJB component-defining annotation or declared as an EJB bean class in `B100`F9d9ejb-jar.xml`f`b.
No special declaration, such as an annotation, is required to define a managed bean.
A MBean can notify the MBeanServer of its internal changes (for the attributes) by implementing the `B100`F9d9javax.management.NotificationEmitter`f`b. The application interested in the MBean's changes registers a listener (`B100`F9d9javax.management.NotificationListener`f`b) to the MBeanServer. Note that JMX does not guarantee that the listeners will receive all notifications.`:cite-ref-8[`F5bf`_`[8`#cite-note-8]`_`f]
>>>Types
There are two basic types of MBean:
• `*Standard MBeans`* implement a business interface containing setters and getters for the attributes and the operations (i.e., methods).
• `*Dynamic MBeans`* implement the `B100`F9d9javax.management.DynamicMBean`f`b interface that provides a way to list the attributes and operations, and to get and set the attribute values.
Additional types are `*Open MBeans`*, `*Model MBeans`* and `*Monitor MBeans`*. `*Open MBeans`* are dynamic MBeans that rely on the basic data types. They are self-explanatory and more user-friendly. `*Model MBeans`* are dynamic MBeans that can be configured during runtime. A generic MBean class is also provided for dynamically configuring the resources during program runtime.
A MXBean (`*Platform MBean`*) is a special type of MBean that `F33f`_`[reifies`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Reification_(computer_science)]`_`f `F33f`_`[Java virtual machine`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_virtual_machine]`_`f subsystems such as `F33f`_`[garbage collection`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Garbage_collection_(computer_science)]`_`f, `F33f`_`[JIT compilation`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=JIT_compilation]`_`f, `F33f`_`[memory pools`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Memory_pools]`_`f, `F33f`_`[multi-threading`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Thread_(computer_science)]`_`f, etc.
A MLet (`*Management applet`*) is a utility MBean to load, instantiate and register MBeans in a MBeanServer from an `F33f`_`[XML`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=XML]`_`f description. The format of the XML descriptor is:`:cite-ref-9[`F5bf`_`[9`#cite-note-9]`_`f]
`B100`F9d9 <MLET CODE = ''class'' | OBJECT = ''serfile''`f`b
`B100`F9d9 ARCHIVE = ''archiveList''`f`b
`B100`F9d9 [CODEBASE = ''codebaseURL'']`f`b
`B100`F9d9 [NAME = ''objectName'']`f`b
`B100`F9d9 [VERSION = ''version'']`f`b
`B100`F9d9 >`f`b
`B100`F9d9 [arglist]`f`b
`B100`F9d9 </MLET>`f`b
>>Support
JMX is supported at various levels by different vendors:
• JMX is supported by Java `F33f`_`[application servers`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Application_server]`_`f such as OpenCloud Rhino Application Server [1], `F33f`_`[JBoss`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=JBoss]`_`f, JOnAS, `F33f`_`[WebSphere Application Server`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=WebSphere_Application_Server]`_`f, `F33f`_`[WebLogic`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=WebLogic]`_`f, `F33f`_`[SAP NetWeaver Application Server`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=SAP_NetWeaver_Application_Server]`_`f, `F33f`_`[Oracle Application Server 10g`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Oracle_Application_Server_10g]`_`f and `F33f`_`[Sun Java System Application Server`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Sun_Java_System_Application_Server]`_`f.
• JMX is supported by the UnboundID Directory Server, Directory `F33f`_`[Proxy Server`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Proxy_server]`_`f, and Synchronization Server.`:cite-ref-10[`F5bf`_`[10`#cite-note-10]`_`f]
• `F33f`_`[Systems management`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Systems_management]`_`f tools that support the protocol include `F33f`_`[Empirix`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Empirix]`_`f OneSight, GroundWork Monitor, `F33f`_`[Hyperic`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Hyperic]`_`f, `F33f`_`[HP OpenView`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=OpenView]`_`f, `F33f`_`[IBM Director`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=IBM_Director]`_`f, ITRS Geneos, `F33f`_`[Nimsoft NMS`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Nimsoft]`_`f, `F33f`_`[OpenNMS`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=OpenNMS]`_`f,`:cite-ref-11[`F5bf`_`[11`#cite-note-11]`_`f] `F33f`_`[Zabbix`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Zabbix]`_`f, `F33f`_`[Zenoss Core`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Zenoss_Core]`_`f, and Zyrion, `F33f`_`[SolarWinds`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=SolarWinds]`_`f, Uptime Infrastructure Monitor, and LogicMonitor.`:cite-ref-12[`F5bf`_`[12`#cite-note-12]`_`f]
• JMX is also supported by `F33f`_`[servlet containers`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Java_Servlet]`_`f such as `F33f`_`[Apache Tomcat`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Apache_Tomcat]`_`f.`:cite-ref-13[`F5bf`_`[13`#cite-note-13]`_`f] & `F33f`_`[Jetty (web server)`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Jetty_(web_server)]`_`f
• `F33f`_`[MX4J`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=MX4J]`_`f [2] is Open Source JMX for Enterprise Computing.
• jManage [3] Archived 2020-08-03 at the `F33f`_`[Wayback Machine`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Wayback_Machine]`_`f is an open source enterprise-grade JMX Console with Web and command-line interfaces.
• `F33f`_`[MC4J`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=MC4J]`_`f [4] is an open source visual console for connecting to servers supporting JMX
• snmpAdaptor4j [5] is an open source providing a simple access to MBeans via the SNMP protocol.
• jvmtop is a lightweight open source JMX monitoring tool for the command-line
• `F33f`_`[Prometheus`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Prometheus_(software)]`_`f can ingest JMX data via the JMX exporter`:cite-ref-14[`F5bf`_`[14`#cite-note-14]`_`f] which exposes metrics in Prometheus format.
• `F33f`_`[New Relic`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=New_Relic]`_`f's on-host infrastructure agent collects JMX data`:cite-ref-15[`F5bf`_`[15`#cite-note-15]`_`f] which is shown in various charts in its `F33f`_`[observability`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Observability_(software)]`_`f platform's dashboard.`:cite-ref-16[`F5bf`_`[16`#cite-note-16]`_`f]`:cite-ref-17[`F5bf`_`[17`#cite-note-17]`_`f]
• Jolokia is a Java agent that exposes JMX over HTTP for easy access from non-Java systems.
>>See also
• `F33f`_`[Jini`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Jini]`_`f
• `F33f`_`[Network management`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Network_management]`_`f
• `F33f`_`[Simple Network Management Protocol`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Simple_Network_Management_Protocol]`_`f
>>References
`:cite-note-1`!1.`! `F0af`_`[↑`#cite-ref-1]`_`f "Overview of the Java Dynamic Management Kit". `*docs.oracle.com`*. Retrieved January 12, 2021.
`:cite-note-2`!2.`! `F0af`_`[↑`#cite-ref-2]`_`f JSR 003: JavaTM Management Extensions (JMXTM) Specification
`:cite-note-3`!3.`! `F0af`_`[↑`#cite-ref-3]`_`f JSR 255: JavaTM Management Extensions (JMXTM) Specification, version 2.0
`:cite-note-4`!4.`! `F0af`_`[↑`#cite-ref-4]`_`f JSR 160: JavaTM Management Extensions (JMX) Remote API
`:cite-note-5`!5.`! `F0af`_`[↑`#cite-ref-5]`_`f JSR 262: Web Services Connector for Java Management Extensions (JMX) Agents
`:cite-note-6`!6.`! `F0af`_`[↑`#cite-ref-6]`_`f Using JConsole to Monitor Applications
`:cite-note-7`!7.`! `F0af`_`[↑`#cite-ref-7]`_`f "The MC4J project creates management software for J2EE application servers and other Java applications". Archived from the original on 2007-03-23. Retrieved 2006-08-27.
`:cite-note-8`!8.`! `F0af`_`[↑`#cite-ref-8]`_`f Java Management Extensions (JMX) – Best Practices
`:cite-note-9`!9.`! `F0af`_`[↑`#cite-ref-9]`_`f "MLet (Java 2 Platform SE 5.0)". `F33f`_`[Sun Microsystems`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Sun_Microsystems]`_`f. Retrieved 2008-06-22.
`:cite-note-10`!10.`! `F0af`_`[↑`#cite-ref-10]`_`f UnboundID Corp. Archived 2012-03-06 at the `F33f`_`[Wayback Machine`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Wayback_Machine]`_`f
`:cite-note-11`!11.`! `F0af`_`[↑`#cite-ref-11]`_`f "Home".
`:cite-note-12`!12.`! `F0af`_`[↑`#cite-ref-12]`_`f "JMX Data Collection". `*www.logicmonitor.com`*. Retrieved 2020-11-20.
`:cite-note-13`!13.`! `F0af`_`[↑`#cite-ref-13]`_`f Apache Tomcat 6.0: Monitoring and Managing Tomcat (Tomcat manual)
`:cite-note-14`!14.`! `F0af`_`[↑`#cite-ref-14]`_`f "JMX Exporter". `*`F33f`_`[GitHub`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=GitHub]`_`f`*. 14 February 2022.
`:cite-note-15`!15.`! `F0af`_`[↑`#cite-ref-15]`_`f "JMX monitoring integration | New Relic Documentation". `*docs.newrelic.com`*. Retrieved 2025-01-13.
`:cite-note-16`!16.`! `F0af`_`[↑`#cite-ref-16]`_`f "JVMs page (Java): View app server metrics from JMX | New Relic Documentation". `*docs.newrelic.com`*. Retrieved 2025-01-13.
`:cite-note-17`!17.`! `F0af`_`[↑`#cite-ref-17]`_`f "Introduction to New Relic for Java | New Relic Documentation". `*docs.newrelic.com`*. Retrieved 2025-01-13.
>>Further reading
>>>Articles
• "Enabling Component Architectures with JMX" by Marc Fleury and Juha Lindfors
• "Introducing A New Vendor-Neutral J2EE Management API" by Andreas Schaefer
• "Java in the management sphere" by Max Goff 1999
1. Oct 20
2. Nov 20
3. Dec 29
• JMX/JBoss – The `F33f`_`[microkernel`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Microkernel]`_`f design
• "Manage your JMX-enabled applications with jManage 1.0" by Rakesh Kalra Jan 16, 2006
• "Managing J2EE Systems with JMX and JUnit Archived 2008-05-26 at the `F33f`_`[Wayback Machine`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Wayback_Machine]`_`f" by Lucas McGregor
• Sun Java Overview of Monitoring and Management
• The Java EE 6 Tutorial: About managed beans
>>>Books
• Benjamin G Sullins, `*Mark B Whipple : JMX in Action: You will also get your first JMX application up and running`*, `F33f`_`[Manning Publications`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Manning_Publications]`_`f Co. 2002, `F33f`_`[ISBN`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ISBN_(identifier)]`_`f 1-930110-56-1
• J. Steven Perry: `*Java Management Extensions`*, O'Reilly, `F33f`_`[ISBN`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ISBN_(identifier)]`_`f 0-596-00245-9
• `F33f`_`[Jeff Hanson`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Jeff_Hanson]`_`f: `*Connecting JMX Clients and Servers: Understanding the Java Management Extensions`*, APress L. P., `F33f`_`[ISBN`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ISBN_(identifier)]`_`f 1-59059-101-1
• `F33f`_`[Marc Fleury`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Marc_Fleury]`_`f, Juha Lindfors: `*JMX: Managing J2EE with Java Management Extensions`*, Sams Publishing, `F33f`_`[ISBN`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ISBN_(identifier)]`_`f 0-672-32288-9
>>External links
• JMX 1.4 (JMX 1.4, part of Java 6)
• JMX at JBoss.com
• JMX on www.oracle.com
• JSR 255 (JMX 2.0)
• JSR 3 (JMX 1.0, 1.1, and 1.2)
`c`F0af`_`[↑ Back to top`#top]`_`f`a